Method and Apparatus of Accessing Data of Virtual Machine

ABSTRACT

A methods and device for accessing virtual machine (VM) data are described. A computing device for accessing virtual machine comprises an access request process module, a data transfer proxy module and a virtual disk. The access request process module receives a data access request sent by a VM and adds the data access request to a request array. The data transfer proxy module obtains the data access request from the request array, maps the obtained data access request to a corresponding virtual storage unit, and maps the virtual storage unit to a corresponding physical storage unit of a distributed storage system. A corresponding data access operation may be performed based on a type of the data access request.

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This application is a national stage application of an internationalpatent application PCT/US11/60271, filed Nov. 10, 2011, which claimspriority to Chinese Patent Application No. 201010542916.1, filed on Nov.12, 2010, entitled “METHOD AND DEVICE FOR ACCESSING VIRTUAL MACHINEDATA,” which applications are hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

This disclosure relates to the field of computer technologies. Moreparticularly, the disclosure relates to a method and device foraccessing data on a virtual machine.

BACKGROUND

A virtual machine (VM) is a computer system that simulates functions ofa complete hardware system by using software, and operates in anisolated environment. By implementing VM technologies, a physicalcomputer may emulate one or more virtual computers. Like a physicalcomputer, a VM may, for example, install operating systems as well asapplications and accesses the Internet resources.

In general, data of a VM is stored in a virtual disk of the VM. Thevirtual disk is stored in a physical disk of a local physical computerin the form of mirror documents, logic virtual volumes, logic disks orlogic disk partitions. The VM may access the data by accessing thephysical disk of the local computer. This may present problems, forexample, when the local computer is shut down or damaged.

SUMMARY

This disclosure provides methods and devices for accessing virtualmachine (VM) data. In some aspects, a device may comprise an accessrequest process module, a data transfer proxy module, and a virtualdisk. The access request process module receives a data access requestthat is sent by a VM, and adds the data access request to a requestarray. The data transfer proxy module obtains the data access requestfrom the request array, maps the data access request to a correspondingvirtual storage unit, and maps the virtual storage unit to acorresponding physical storage unit of a distributed storage system. Inthe distributed storage system, a corresponding data access operationmay be performed based on a type of the data access request. In someaspects, the device may further comprise a second-level cache module, athird-level cache module, and/or a data snapshot module.

BRIEF DESCRIPTION OF THE DRAWINGS

The Detailed Description is described with reference to the accompanyingfigures. The use of the same reference numbers in different figuresindicates similar or identical items.

FIG. 1 is a schematic block diagram showing details of an exemplarycomputing device for accessing data of a virtual machine (VM).

FIG. 2 is a schematic diagram showing an exemplary environment foraccessing data of a VM.

FIG. 3 is a schematic block diagram showing an exemplary mappingrelationship.

FIG. 4 is a schematic block diagram showing details of another exemplarycomputing device for accessing data of a VM.

FIG. 5 is a schematic block diagram showing details of yet anotherexemplary computing device for accessing data of a VM.

FIG. 6 is a schematic block diagram showing details of still anotherexemplary computing device for accessing data of a VM.

FIG. 7 is a schematic block diagram showing an exemplary mappingrelationship between virtual disks and physical storage.

FIG. 8 is a flowchart showing an exemplary process of accessing data ofa VM.

FIG. 9 is a flowchart showing another exemplary process of accessingdata of a VM.

FIG. 10 is a flowchart showing yet another exemplary process ofaccessing data of a VM.

FIG. 11 is a schematic block diagram showing details of an exemplarysystem for accessing data of a single VM.

FIG. 12 is a schematic block diagram showing details of an exemplarysystem for accessing data of parallel VMs.

FIG. 13 is a schematic block diagram showing details of an exemplarysystem for implementing a VM migration.

FIG. 14 is a schematic block diagram showing details of an exemplarysystem for accessing data of VMs by implementing shared storage.

DETAILED DESCRIPTION

As discussed above, under conventional virtual machine (VM)technologies, the state of local physical computers may affect securityand reliability of data of VMs. Because of security and reliabilityconcerns, development and applications of VM techniques are dramaticallylimited. This disclosure describes various exemplary ways of improvingsecurity and reliability of accessing VM data, for example, by mappingvirtual storage of a virtual disk to physical storage of a distributedstorage system. This disclosure may provide a data transmission channelbetween a VM and a distributed storage system, and, therefore, provideoverall, consistent, complete, high-efficient, secured, and compatibledata access services.

FIG. 1 is a schematic block diagram showing details of the exemplarycomputing device 100 for accessing data of a VM. The computing device100 may be configured as any suitable device. In one exemplaryconfiguration, the computing device 100 includes one or more processors105, input/output interfaces 106, network interface 107, and memory 104.

The memory 104 may include computer-readable media in the form ofvolatile memory, such as random-access memory (RAM) and/or non-volatilememory, such as read only memory (ROM) or flash RAM. The memory 104 isan example of computer-readable media.

Computer-readable media includes volatile and non-volatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer readable instructions, datastructures, program modules, or other data. Examples of computer storagemedia includes, but is not limited to, phase change memory (PRAM),static random-access memory (SRAM), dynamic random-access memory (DRAM),other types of random-access memory (RAM), read-only memory (ROM),electrically erasable programmable read-only memory (EEPROM), flashmemory or other memory technology, compact disk read-only memory(CD-ROM), digital versatile disks (DVD) or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other non-transmission medium that canbe used to store information for access by a computing device. Asdefined herein, computer-readable media does not include transitorymedia such as modulated data signals and carrier waves.

Turning to the memory 104 in more detail, the memory 104 may store anaccess request process module 101, a data transfer proxy module 102 anda virtual disk 103, and one or more applications for implementing all ora part of accessing data of a VM (not shown in FIG. 1). The accessrequest process module 101 receives a data access request from a VM andadds the data access request to a request array. In some embodiments,the data access request maps to a virtual storage unit of the virtualdisk 103, and the virtual storage unit maps to a physical storage unitof a distributed storage system (See FIG. 2).

The data transfer proxy module 102 obtains the data access request fromthe request array, maps the data access request to a correspondingvirtual storage unit, and maps the virtual storage unit to acorresponding physical storage unit of the distributed storage system.In some embodiments, the data transfer proxy module 102 may, based on atype of the data access request, perform operations on correspondingdata on the physical storage unit of the distributed storage system.

Suppose that the type of obtained data access request is “write data”and that the mapped physical storage unit information is sent to thedistributed storage system. As a result, the distributed storage systemoperates “write data” based on the physical storage unit information. Ifthe type of obtained data access request is “read data,” the data isread from the distributed storage system based on the physical storageunit information, and the data can be fed back to the VM.

FIG. 2 is a schematic diagram showing an exemplary environment 200 thatmay include a virtual machine, a computing device (e.g., the computingdevice 100) and a distributed storage system. Data in a virtual disk ofa VM can be saved in physical disks of multiple physical computers in adistributed storage system based on the mapping techniques. As a result,a backup associated with the VM data can be implemented, and thesecurity and the reliability of the stored VM data can be improved.

FIG. 3 is a schematic block diagram showing an exemplary mappingrelationship 300. In some embodiments, the data access request in therequest array is mapped to a virtual storage unit in a virtual disk, andthe virtual storage unit further is mapped to a physical storage unit ina distributed storage system. As shown in FIG. 3, the data accessrequest may include a request type, an initial address of data, a datasize, and an address size. The request type indicates a requestedoperation on the data (e.g., read, write or delete). The initial addressof data indicates an initial address of the data in the virtual storageunit of the virtual disk of to which the data access request accesses. Avirtual storage size of data may be obtained based on the initialaddress of data and the size of data. The storage size indicates astorage size for caching data associated with the data access request inmemory of a physical computer associated with the VM.

A virtual storage unit mapped to a data access request can be determinedbased on the initial address of the data and the size of the dataassociated with the data access request. The virtual storage unit isconfigured to save the data associated with the data access request.Based on the virtual storage unit and the associated mappingrelationship, a physical storage unit of the distributed storage systemcan be determined. The physical storage unit associated with the dataaccess request is determined based on the initial address and the sizeof the data associated with the data access request. A data accesschannel from the VM to the distributed storage system is thenestablished, and, therefore, the data access from the VM to thedistributed storage system can be implemented.

In some embodiments, the data transfer proxy module 102 may obtainindividual data access requests from a request array, for example, aftergetting notification from the access request process module 101. Thedata transfer proxy module 102 may actively access the request arrayperiodically to obtain data access requests. The data access requestsare then firstly mapped to corresponding virtual storage units, whichare further mapped to corresponding physical storage units of adistributed storage system. The physical storage units can be determinedbased on the mapping techniques. As accessing VM data described in thisdisclosure requires merely a mapping relationship without copying data,system resources can be saved by using less time and storage.

In some embodiments, a request array may correspond to a thread withrespect to multithreading applications. Suppose that 16 threads areconcurrently activated and that each thread implements functions of thedata transfer proxy module 102. As a result, 16 data transfer proxymodules can be concurrently activated in the computing device 100 foraccessing data of a VM.

FIG. 4 is a schematic block diagram showing details of an exemplarycomputing device 400 that may include, similar to the device of FIG. 1,the access request process module 101, the data transfer proxy module102, and the virtual disk 103. In this FIG. 4 implementation, thecomputing device 400 further includes a second-level cache module 404.In some embodiments, the access request process module 101 determineswhether a second-level cache stores the data associated with the dataaccess request after the access request process module 101 receives thedata read request from a VM. If yes, the data can be read from the cachedirectly. If no, the access request process module adds the data accessrequest to a request array. After the data transfer proxy module 102reads data, the second-level cache module 404 creates a second-levelcache slot to store the data.

For example, when the access request process module 101 receives a dataread request (e.g., a data access request indicating to read data A),the access request process module 101 searches a second-level cache. Ifthe second-level cache stores data A, data A is read from thesecond-level cache directly. Otherwise, the data read request is addedto the request array so that data A can be read from a distributedstorage system based on the mapping techniques. After the data transferproxy module 102 reads data A, the second-level cache module 404 createsa second-level cache slot to store data A. In some embodiments, thesecond-level cache slot is created in advance, and a cache item A iscreated in the second-level cache slot for data A. The cache item Acreated for data A is then added to a cache pool of the second-levelcache. Therefore, when the data transfer proxy module 102 reads newdata, the second-level cache module 404 creates a new cache item in thesecond-level cache and adds the new cache item into the cache pool ofthe second-level cache.

In some embodiments, the second-level cache is physical memory of alocal physical computer, expediting accessing data of a VM. In someembodiments, data in a virtual disk of a VM can be saved in physicaldisks of multiple physical computers of a distributed storage systembased on the mapping techniques, improving security and reliability ofdata stored in a VM. In some embodiments, reading data and caching thedata in a front-end strategy system can be conducted at the same time tofurther increase the speed of accessing data of a VM.

FIG. 5 is a schematic block diagram showing details of an exemplarycomputing device 500 that. Similar to the devices of FIGS. 1 and 4, mayinclude the access request process module 101, the data transfer proxymodule 102, and the virtual disk 103. In the FIG. 5 implementation, thedevice 500 also includes a third-level cache module 505. In someembodiments, the data transfer proxy module 102 determines whether thecache stores the data associated with a data access request after thedata transfer proxy module 102 obtains the data read request from therequest array. If yes, the data can be read from the cache slotdirectly. If no, the data transfer proxy module 102 maps the data readrequest to a corresponding virtual storage unit and maps the virtualstorage space to a corresponding physical storage unit. After the datatransfer proxy module 102 reads data, the third-level cache module 505creates a third-level cache slot to store the data. In some embodiments,the data transfer proxy module 102 may further perform operations on thedata associated with the data access request.

For example, when the data transfer proxy module 102 obtains a data readrequest (e.g., a data access request indicating to read data C), thedata transfer proxy module 102 searches a third-level cache. If thethird-level cache retains data C, data C is read from the third-levelcache directly. Otherwise, the obtained data read request is mapped to acorresponding virtual storage unit that is further mapped to acorresponding physical storage unit. After the data transfer proxymodule 102 reads data C, the third-level cache module 505 creates athird-level cache slot to store data C. In some embodiments, thethird-level cache slot is created in advance, and a cache item C iscreated in the third-level cache slot for data C. The cache item C isthen added to a cache pool of the third-level cache. Therefore, when thedata transfer proxy module 102 reads new data, the third-level cachemodule 505 creates a new cache item in the third-level cache and addsthe new cache item into the cache pool of the third-level cache.

In some embodiments, the third-level cache slot is physical memory of alocal physical computer, expediting accessing data of a VM. In someembodiments, the computer device 500 may include both the second-levelcache module 404 and the third-level cache module 505. In thissituation, the access request reaches the access request process module101 first, and processing memory data is faster than processing diskdata. As a result, the second-level cache slot may be located inphysical memory of a local physical computer, and the third-level cacheslot may be located in a physical disk of a local physical computer tofurther expedite accessing data of a VM. In some embodiments, data in avirtual disk of a VM can be saved in physical disks of multiple physicalcomputers of a distributed storage system based on the address mapping.Therefore, security and reliability of stored VM data can be improved.In some embodiments, reading data and caching the data in a back-endstrategy system can be conducted at the same time to further increasethe speed of accessing data of a VM.

FIG. 6 is a schematic block diagram showing details of another possibleimplementation of an exemplary computing device 600. The computingdevice 600 includes an access request process module 101, a datatransfer proxy module 102, a virtual disk 103, and a data snapshotmodule 606. As shown in FIG. 6, the virtual disk 103 may include avirtual disk partition of original data, a virtual disk partition ofsnapshot data and a mapping partition. In some embodiments, data in avirtual disk can be saved as snapshot data at a certain time to backupthe data in other storage. The data snapshot module 606 obtains avirtual storage slot of the virtual disk partition of original data anda virtual storage slot of the virtual disk partition of snapshot datafrom the mapping partition.

In some embodiments, the computing device 600 may include the exportmodule 607 that maps the virtual storage slot of the original data andthe virtual storage slot of the snapshot data that is obtained by thedata snapshot module 606 to corresponding physical storage units of adistributed storage system.

In some embodiments, the computing device 600 includes an import module(not shown) that maps physical storage units of the distributed storagesystem to virtual disk partitions of original data and virtual diskpartitions of snapshot data, after an import request is received. Forexample, when original data and snapshot data in a distributed storagesystem need to be exported to other VMs, the import module may mapphysical storage units of the distributed storage system to virtual diskpartitions of the original data and virtual disk partitions of thesnapshot data in other VMs. As a result, the data is exported to otherstorage systems.

FIG. 7 is a schematic block diagram showing an exemplary mappingrelationship between virtual disks and physical storage. In someembodiments, virtual storage units of the virtual disk partition oforiginal data and the virtual disk partition of snapshot data areretained in the mapping partition. The virtual storage units areobtained from the mapping partition when the data snapshot module 606receives a data snapshot request. The export module 607 maps the virtualstorage units to physical storage units of a distributed storage systemso that the original data and the snapshot data can be obtained from thephysical storage units of the distributed storage system, and that adata snapshot at a certain time can be obtained based on the originaldata and the snapshot data.

In some embodiments, the sector codes in the device for accessing VMdata may include Vm_id, Image_id, Vbd_id, Par_id and Cell_id. Vm_id(32-bit) is the number of a VM; Image_id (32-bit) is the number of anassociated mirrored document and can indicate imported snapshot data;Vbd_id (8-bit) is the number of a virtual hard drive; Par_id (8-bit) isthe number of a partition; and, Cell_id (64-bit) is the number of asector. Vm_id, Image_id, Vbd_id and Par_id are configured by a managingsystem to include information associated with relationship and attributeof a computing device for accessing VM data. In some embodiments, thefront-end strategy system combines these codes to uniquely identifysector locations of distributed storage units after receiving therequest from an upper-level document system. Then, read/write operationson the sectors are performed based on these codes.

FIGS. 8-10 are flowcharts showing exemplary processes of accessing dataof a VM. The processes are illustrated as a collection of blocks inlogical flowcharts, which represent a sequence of operations that can beimplemented in hardware, software, or a combination. For discussionpurposes, the processes are described with reference to the computingdevices 100, 400, 500 and/or 600 shown in FIGS. 1 and 4-6, the computingenvironment 200 shown in FIG. 2, and the mapping relationships 300 and700 shown in FIGS. 3 and 7. However, the processes may be performedusing different environments and devices. Moreover, the environments anddevices described herein may be used to perform different processes.

FIG. 8 is a flowchart showing an exemplary process of accessing data ofa VM. At 801, the access request process module 101 receives a dataaccess request that is sent by a VM. At 802, the access request processmodule 101 adds the data access request to a request array. The dataaccess request maps to a virtual storage unit in a virtual disk, and thevirtual storage unit maps to a physical storage unit in a distributedstorage system. At 803-805, the data transfer proxy module 102 obtainsthe data access request from the request array, maps the data accessrequest to a corresponding virtual storage unit, and maps the virtualstorage unit to a corresponding physical storage unit. At 806, thetransfer proxy module 102 may obtain data from the physical storageunit. In some embodiments, 801-806 may be repeated until all data accessrequests in the request array are processed.

The distributed storage system may operate a corresponding data accessoperation in the physical storage unit based on a type of data accessrequest. For example, if the type of the obtained data access request is“write data”, the distributed storage system operates “write data” basedon the physical storage unit information that is sent to thedistribution storage system from the computing device 100. If the typeof the obtained data access request is “read data”, the data is readfrom the distributed storage system based on the physical storage unitinformation. As a result, the data can be fed back to the VM associatedwith the date access request.

FIG. 9 is a flowchart showing an exemplary process of accessing data ofa VM. At 901, the access request module 101 receives a data accessrequest that is sent by a VM. At 902, the access request module 101determines whether a second-level cache unit stores the data associatedwith the data access request. If the data is stored (i.e., the “yes”branch from 902), the data transfer proxy module 102 directly reads thedata at 903. If the data is not stored (i.e., the “no” branch from 902),the data transfer proxy module 102 obtains the data access request froma request array after the data access request is added to the requestarray at 904. At 905 and 906, the data transfer proxy module 102 mapsthe data access request to a corresponding virtual storage unit, andmaps the virtual storage unit to a corresponding physical storage unit.At 907, the data transfer proxy module 102 obtains the data associatedwith the data access request. At 908, the second-level cache module 404creates a second-level cache slot to store the data. In someembodiments, 901-908 may be repeated until all data access requests inthe request array are processed.

FIG. 10 is a flowchart showing an exemplary process of accessing data ofa VM. In some embodiments, to expedite data access processes, athird-level cache may be created after a corresponding data readoperation is performed in the mapped physical storage units based on theassociated data read request. At 1001, the data transfer proxy module102 obtains a data access request from a request array. At 1002, thedata transfer proxy module 102 determines whether a third-level cachestores the data associated with the data access request. If the data isstored (i.e., the “yes” branch from 1002), the data transfer proxymodule 102 reads the data directly from the third-level cache at 1003.If the data is not stored in the third-level cache (i.e., the “no”branch from 1002), the data transfer proxy module 102 maps the dataaccess request to a virtual storage unit, and maps the virtual storageunit to a physical storage unit of a distributed storage system. At1006, the data transfer proxy module 102 obtains the data from thedistributed storage system. At 1007, a third-level cache module createsa third-level cache slot to store the data. In some embodiments,1001-1007 may be repeated until all data access request in the requestarray are processed.

In some embodiments, the processes described above may further includeobtaining snapshot data associated with the data access request. Forexample, the data snapshot module 606 may obtain a virtual storage unitof a virtual disk partition of original data and a virtual storage unitof a virtual disk partition of snapshot data from a mapping partition ofthe virtual disk after a snapshot request is received, map the virtualstorage unit of the original data and the virtual storage unit of thesnapshot data to corresponding physical storage units of the distributedstorage system after an export request is received.

In some embodiments, reading and caching the data associated with thedata access request in the front-end strategy system can be conducted atthe same time. For example, after the access request process module 101receives the next data access request, the data associated with the dataaccess request can be read from a cache that stores the data, expeditingaccessing data of a VM. In some embodiments, reading and caching thedata associated with the data access request in the back-end mechanismsystem can be conducted at the same time. For example, after the datatransfer proxy module 102 obtains the next data access request, the datacan be read from a cache that stores the data, expediting accessing dataof a VM.

In some embodiments, the processes described above may be performed indifferent environments and devices, for example, a single virtualmachine start, a multiple-machine parallel virtual machines start, avirtual machine migration, and/or shared storage. FIGS. 11-14 show fourdifferent embodiments to illustrate these four cases.

FIG. 11 is a schematic block diagram showing details of an exemplarysystem 1100 for accessing data of a single VM. The system 1100 mayinclude a computing device, similar to the devices of FIGS. 1, 4 and 5,a VM, and physical storage of a distributed system. By implementing asingle virtual machine start, the start time and the response speed of aVM are improved.

FIG. 12 is a schematic block diagram showing details of an exemplarysystem 1200 for accessing data of parallel VMs. The system 1200 mayinclude a computing device, similar to the devices of FIGS. 1, 4 and 5,a plurality of parallel VMs, and physical storage of a distributedsystem. By implementing a multiple-machine parallel virtual machinesstart, the start time and the response speed of a VM are improved too.

FIG. 13 is a schematic block diagram showing details of an exemplarysystem 1300 for implementing a VM migration. The System 1300 may includea plurality of computing devices, similar to the devices of FIGS. 1, 4and 5, a plurality of corresponding VMs, and physical storage of adistributed system. By implementing a virtual machine migration, theamount of data migration is reduced and the migration speed isincreased.

FIG. 14 is a schematic block diagram showing details of an exemplarysystem 1400 for accessing data of VMs by implementing shared storage.The system 1400 may include a plurality of computing devices, similar tothe devices of FIGS. 1, 4 and 5, a plurality of corresponding VMs, and aplurality of physical storage units of distributed systems (i.e.,physical storage A, B and C). In the system 1400, the distributedsystems are installed on servers, and each server node stores data inlocal hard drives (not shown). Each server node may construct a storagearea network (SAN) by employing the plurality of computing devices ofFIG. 14 for accessing VM data. Accordingly, SAN shared software may beconfigured to implement the shared storage devices and to manage datadevelopment access in a group. By way of example and not limitation, theSAN shared software may include pNFS/GFS2, and CIFS for Windows system.

The embodiments in this disclosure are merely for illustrating purposesand are not intended to limit the scope of this disclosure. A personhaving ordinary skill in the art would be able to make changes andalterations to embodiments provided in this disclosure. Any changes andalterations that persons with ordinary skill in the art would appreciatefall within the scope of this disclosure.

What is claimed is:
 1. A device for accessing virtual machine data, thedevice comprising: memory; one or more processors coupled to the memory;a virtual disk, stored in the memory, that includes a virtual storageunit; an access request process module, stored in the memory andexecutable by the one or more processors, that: receives a data accessrequest from a virtual machine, and adds the data access request to arequest array; and a data transfer proxy module, stored in the memoryand executable by the one or more processors, that: obtains the dataaccess request from the request array, and maps the data access requestto the virtual storage unit that corresponds to a physical storage unitof a storage system.
 2. The device as recited in claim 1, wherein thedata transfer proxy module further performs a data access operation ondata associated with the data access request based on a request typethat is included in the data access request.
 3. The device as recited inclaim 1, wherein the access request process module further determinesthat cache storage retains data associated with the data access requestafter the receiving of the data access request from the virtual machine,and the data transfer proxy module subsequently obtains the data fromthe cache storage.
 4. The device as recited in claim 1, wherein the datatransfer proxy module determines that cache storage retains dataassociated with the data access request after the obtaining of the dataaccess request from the request array, and subsequently obtains the datafrom the cache storage.
 5. The device as recited in claim 1, furthercomprising a cache module stored in the memory and executable by the oneor more processors, wherein the access request process module determinesthat cache storage does not store data associated with the data accessrequest after the receiving of the data access request from the virtualmachine, and the cache module subsequently creates a cache slot of thecache storage to store the data.
 6. The device as recited in claim 1,further comprising a cache module stored in the memory and executable bythe one or more processors, wherein the data transfer proxy moduledetermines that cache storage does not store data associated with thedata access request after the obtaining of the data access request fromthe request array, and the cache module subsequently creates a cacheslot of the cache storage to store the data.
 7. The device as recited inclaim 6, wherein the cache storage comprises local memory or a localphysical disk.
 8. The device as recited in claim 1, further comprising adata snapshot module stored in the memory and executable by the one ormore processors, wherein the virtual disk comprises a virtual diskpartition of original data, a virtual disk partition of snapshot dataand a mapping partition, and the data snapshot module obtains a virtualstorage unit of the virtual disk partition of original data and avirtual storage unit of the virtual disk partition of snapshot data fromthe mapping partition.
 9. The device as recited in claim 8, furthercomprising an export module, stored in the memory and executable by theone or more processors, that maps the virtual storage unit of originaldata and the virtual storage unit of snapshot data to physical storagesunits of the distributed storage system after an export request isreceived.
 10. The device as recited in claim 8, further comprising animport module, stored in the memory and executable by the one or moreprocessors, that maps physical storages units of the distributed storagesystem to the virtual storage unit of original data and the virtualstorage unit of snapshot data after an import request is received. 11.The device as recited in claim 8, wherein the data snapshot modulefurther obtains the original data and the snapshot data from thephysical storages units.
 12. A computer-implemented method for accessingvirtual machine data, comprising: receiving a data access request from avirtual machine; placing the data access request in a request array;obtaining the data access request from the request array; mapping thedata access request to a virtual storage unit of a virtual disk; mappingthe virtual storage unit to physical storage in a distributed storagesystem; and performing a data operation associated with the data accessrequest.
 13. The computer-implemented method as recited in claim 12,wherein the data access request includes a request type, an initialaddress of data storage, and a data size.
 14. The computer-implementedmethod as recited in claim 12, wherein the performing comprisesperforming the data operation based on the request type.
 15. Thecomputer-implemented method as recited in claim 12, further comprising:creating a cache slot to store data associated with the data accessrequest after obtaining the data from the distributed storage system ifthe data is not stored in cache storage; and obtaining the data from thecache storage if the data is stored in the cache storage.
 16. Thecomputer-implemented method as recited in claim 12, further comprising:obtaining a virtual storage unit of a virtual disk partition of originaldata and a virtual storage unit of a virtual disk partition of snapshotdata from a mapping partition after a snapshot request is received;mapping the virtual storage unit of original data and the virtualstorage unit of snapshot data to physical storage units of thedistributed storage system after an export request is received; andobtaining the original data and the snapshot data from the distributedstorage system.
 17. One or more computer-readable media encoded withinstructions that, when executed by a processor of a computer, performacts comprising: receiving a data access request from a virtual machine,the data access request mapping to a virtual storage unit of a virtualdisk that maps to a physical storage unit of a distributed storagesystem; obtaining data from the physical storage unit based on the dataaccess request; creating a front-end cache slot to store the data inresponse to determination that front-end cache storage does not storesthe data; and creating a back-end cache slot to store the data inresponse to determination that back-end cache storage does not storesthe data.
 18. The one or more computer-readable media as recited inclaim 17, wherein the obtaining data, the creating of the front-endcache slot and the creating of the back-end cache slot are performedsimultaneously.
 19. The one or more computer-readable media as recitedin claim 18, wherein, the front-end cache slot is located in memory of alocal computing device, and the back-end cache slot is located on aphysical disk of one local computing device.
 20. The one or morecomputer-readable media as recited in claim 17, further comprising:obtaining a virtual storage unit of a virtual disk partition of originaldata and a virtual storage unit of a virtual disk partition of snapshotdata from the mapping partition after receiving a data snapshot request;mapping the virtual storage unit of original data and the virtualstorage unit of snapshot data to physical storages units of thedistributed storage system after receiving an export request; andobtaining the original data and the snapshot data from the distributedstorage system.